Log deployment IDs and lifecycle event with every line#326
Open
mpdude wants to merge 1 commit intoaws:masterfrom
Open
Log deployment IDs and lifecycle event with every line#326mpdude wants to merge 1 commit intoaws:masterfrom
mpdude wants to merge 1 commit intoaws:masterfrom
Conversation
Author
|
@NsTremblay What do you think about this? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR amends the log format so that the deployment ID and the lifecycle event are added to every line.
This makes logfile aggregation/processing much easier, since it is no longer necessary to statefully follow log lines to be able to infer the lifecycle event.
Additionally, it is now possible to follow just the
/opt/codedeploy-agent/deployment-root/deployment-logs/codedeploy-agent-deployments.loglog and find all events in one place, while still being able to relate them to deployments and lifecycle phases for every single line.